Managing a set of blocks in a storage system

ABSTRACT

Disclosed aspects include management of a set of blocks in a storage system. A set of write requests is initiated to the set of blocks. In response to the set of write requests, a set of expiration metadata for the set of blocks is established. Based on the set of expiration metadata, an expiration event is detected. In response to detecting the expiration event, an expiration operation on the set of blocks is processed.

BACKGROUND

This disclosure relates generally to computer systems and, moreparticularly, relates to managing a set of blocks in a storage system.The amount of data that needs to be managed by enterprises is growing atan extremely high rate. Management of storage environments may need tobe performed with as few errors as possible. As data needing to bemanaged increases, the need for management efficiency may increase.

SUMMARY

Aspects of the disclosure include policy-based data management at theblock level within a storage subsystem. The policies allow for data tobe archived or deleted after a specific amount of time passes aftercreation or last reference. For example, aspects disclosed include datastorage archival and expiration management at the block level by a datastorage controller to allow associating blocks of different host filesbased on common expiration.

Disclosed aspects include management of a set of blocks in a storagesystem. A set of write requests is initiated to the set of blocks. Inresponse to the set of write requests, a set of expiration metadata forthe set of blocks is established. Based on the set of expirationmetadata, an expiration event is detected. In response to detecting theexpiration event, an expiration operation on the set of blocks isprocessed.

In embodiments, the set of expiration metadata includes first expirationmetadata for a first block of a first file. The set of blocks includesboth the first block and a second block of a second file. The first filemay be different from the second file. In embodiments, the set of blocksincludes a specific block (e.g., first block) having a header configuredto include specific expiration metadata (e.g., first expirationmetadata). In embodiments, a data storage controller is used toestablish the set of expiration metadata for the set of blocks.

Aspects of the disclosure include creating, based on the set ofexpiration metadata, an expiration stack for the set of blocks. Theexpiration stack may be organized based on a temporal feature. Thetemporal feature can include a common expiration trigger for the set ofexpiration metadata. In embodiments, the expiration stack may beorganized using a first-in-first-out order. The expiration stack can beused to process the expiration operation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a cloud computing node according to embodiments;

FIG. 1B depicts a cloud computing environment according to embodiments;

FIG. 1C depicts abstraction model layers according to embodiments;

FIG. 2 is a flowchart illustrating a method for managing a set of blocksin a storage system according to embodiments; and

FIG. 3 shows modules of a system for managing a storage facilityaccording to embodiments.

DETAILED DESCRIPTION

Aspects of the disclosure include policy-based data management at theblock level within a storage subsystem. Management policies areconstructed at the block level. Diverse policies control how blocks ofdata are expired or moved to other forms of storage media. The storagemedia can include other disks, tape, or object stores. The policiesallow for data to be archived or deleted after a specific amount of timepasses after creation or last reference. Such policy information anddata age or activity is then used to remove specific blocks or ranges ofblocks of data. For example, aspects disclosed include data storagearchival and expiration management at the block level by a data storagecontroller to allow associating blocks of different host files based oncommon expiration.

Traditionally, data has been managed at the file level. Such traditionalmanagement includes operations such as migration and expiration.However, such operation within the storage subsystem at a block levelmay be desired. Block level of management with the storage subsystem mayprovide performance or efficiency benefits along with reduced overallstorage cost for storage utilization and vitalization. Such aspects mayhave positive impacts on user and application involvement. User maydesire to be able to define different policies for different types ofdata. For example, a user e-mail may have a different retention policythan organization tax documents. As data becomes more virtualized incloud environments, providing logic at the block level within thestorage subsystem can have positive impacts on data management in oroutside of the cloud.

Aspects of the disclosure include a method, system, and computer programproduct for managing a set of blocks in a storage facility (i.e.,storage system). The method, system, and computer program product maywork on a number of operating systems. A set of write requests isinitiated to the set of blocks. In response to the set of writerequests, a set of expiration metadata for the set of blocks isestablished. Based on the set of expiration metadata, an expirationevent is detected. In response to detecting the expiration event, anexpiration operation on the set of blocks is processed.

In embodiments, the set of expiration metadata includes first expirationmetadata for a first block of a first file. In addition, the set ofexpiration metadata may include second expiration metadata for a secondblock of a second file. The set of blocks includes both the first blockand the second block. The first file may be different from the secondfile. In embodiments, the set of blocks includes a specific block (e.g.,first block) having a header configured to include specific expirationmetadata (e.g., first expiration metadata). In embodiments, a datastorage controller is used to establish the set of expiration metadatafor the set of blocks. Establishing the set of expiration metadata forthe set of blocks can include creating the set of expiration metadata,writing the set of expiration metadata to a set of headers of the set ofblocks, and storing the set of expiration metadata in a data storecommunicatively coupled with the data storage controller.

Aspects of the disclosure include creating, based on the set ofexpiration metadata, an expiration stack for the set of blocks. Theexpiration stack may be organized based on a temporal feature. Thetemporal feature can include a common expiration trigger for the set ofexpiration metadata. In embodiments, the expiration stack may beorganized using a first-in-first-out order. The expiration stack can beused to process the expiration operation.

In embodiments, detecting an expiration event based on the set ofexpiration metadata includes various aspects. The set of expirationmetadata may be analyzed to identify an expiration trigger that is basedon a temporal feature. Monitoring for the expiration trigger can occur.In response to monitoring for the expiration trigger, accomplishment ofthe expiration trigger may be determined. In response to determiningaccomplishment of the expiration trigger the expiration event can beinstantiated.

The storage system may include a set of cloud nodes configured to storethe set of blocks based on the set of expiration metadata. Inembodiments, the set of expiration metadata includes both firstexpiration metadata for a first block of a first file and secondexpiration metadata for a second block of a second file, the set ofblocks includes both the first block and the second block, and the firstfile is different from the second file. As such, by comparing the firstexpiration metadata and the second expiration metadata, a commonexpiration trigger for the first and second blocks may be determined.When the first and second blocks share a common expiration trigger, aconcurrent expiration operation for the first and second blocks may beinitiated. Processing the expiration operation on the set of blocks (orthe concurrent expiration operation for the first and second blocks) mayinclude removing the set of blocks from the storage system. Altogether,aspects of the disclosure provide a methodology for managing a set ofblocks that may provide performance or efficiency benefits.

It is understood in advance that although this disclosure includes adetailed description regarding cloud computing, implementation of theteachings recited herein are not limited to a cloud computingenvironment. Rather, embodiments of the disclosure are capable of beingimplemented in conjunction with any other type of computing environmentnow known or later developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or data center).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting for loadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1A, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the disclosuredescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1A, computer system/server 12 in cloud computing node10 is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the disclosure.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the disclosure as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 1B, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 1B are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 1C, a set of functional abstraction layersprovided by cloud computing environment 50 (FIG. 1B) is shown. It shouldbe understood in advance that the components, layers, and functionsshown in FIG. 1C are intended to be illustrative only and embodiments ofthe disclosure are not limited thereto. As depicted, the followinglayers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and managing a set of blocks. Managing a set of blocks mayprovide data storage archival and expiration management at the blocklevel. A data storage controller may be used to allow associating blocksof different host files based on common expiration.

FIG. 2 is a flowchart illustrating a method 200 for managing data in astorage system according to embodiments. Aspects of method 200 mayinclude policy-based data management at the block level. The policiesinfluence how blocks of data are expired or moved to other forms ofstorage media. The policies allow for data to be archived or deletedafter a specific amount of time passes after creation or last reference.Such data of policy and data age or activity is then be used to removespecific blocks or ranges of blocks of data. Method 200 may begin atblock 201.

At block 203, a set of write requests is initiated to the set of blocks.Subsequently at block 207, the set of blocks is written with data of adata type. In response to the set of write requests being initiated, aset of expiration metadata for the set of blocks is established at block210. The set of expiration metadata can include a retention policy(e.g., a time span of how long to keep the set of blocks). The retentionpolicy can be based on a creation temporal feature (e.g., creationtimestamp), a last-referenced temporal feature (e.g., a staleness valuebased on a usage timestamp), or a combination of temporal features thatmay include reference frequency information (e.g., more frequentlyreferenced data may be retained for a longer time span).

In embodiments, the set of expiration metadata includes first expirationmetadata for a first block of a first file. In addition, the set ofexpiration metadata includes second expiration metadata for a secondblock of a second file. The set of blocks includes both the first blockand the second block. The first file may be different from the secondfile. Thus, operations may be handled at the block level rather than thefile level even with separate files. Analysis of the data to be writtenby the set of write requests may be efficiently bypassed becauseexpiration can be handled without such analysis (e.g., the substance ofthe write requests need not be analyzed because, for example, aretention policy based on a temporal feature may be utilized).

In embodiments, the set of blocks includes a specific block (e.g., firstblock) having a header configured to include specific expirationmetadata (e.g., first expiration metadata) such as at block 212. Theheader, for example, includes a policy regarding block expiration andmay be set at creation of the block. Such as at block 214, blocks may bespatially located according to the policy. Use of the header permitsdispersal of blocks with similar policies across a storage media or aset of cloud nodes. In embodiments, dispersal may provide efficiencybenefits, for example, when using a set of cloud nodes across a largegeographic region. In other embodiments, data can be grouped togetherbased on headers having similar policies. Certain embodiments mayinclude a combination of grouping and dispersing similar policies basedon user specifications. For example, in a cloud-based environment, auser may want sensitive personnel information with a given retentionpolicy grouped in a particular region while publicly availableinformation with the given retention policy may be dispersed across manyregions.

In embodiments, a data storage controller is used to establish the setof expiration metadata for the set of blocks. Establishing the set ofexpiration metadata for the set of blocks includes creating the set ofexpiration metadata (e.g., generating temporal features such as creationor use dates). Establishing the set of expiration metadata for the setof blocks can include writing the set of expiration metadata to a set ofheaders of the set of blocks (e.g., assigning a chosen policy to aheader using an access operation). Establishing the set of expirationmetadata for the set of blocks can include, such as at block 216,storing or saving the set of expiration metadata in a data storecommunicatively coupled with the data storage controller (e.g., savingin a catalog or list that may be linked to the data storage controlleror part of the data storage controller).

Aspects of the disclosure include creating, based on the set ofexpiration metadata, an expiration stack for the set of blocks at block218. The expiration stack includes a stack of metadata (e.g., groupingof metadata of an assembly of the set of blocks). The expiration stackmay be organized based on a temporal feature (e.g., a computed retentiontermination date based on creation/use factors). The temporal featurecan include a common expiration trigger for the set of expirationmetadata (e.g., a number of identical retention dates may produce acommon expiration trigger). In embodiments, the expiration stack may beorganized using a first-in-first-out order (e.g., ordering may be basedon retention termination date and then creation date).

Based on the set of expiration metadata, an expiration event is detectedat block 230. The expiration event can include a criterion being reachedsuch as a date (e.g., retention policy date reached), a business event(e.g., merger-acquisition completion), or a personnel event (e.g., astudent graduates from an institution and no longer needs electronicaccess). In embodiments, detecting an expiration event based on the setof expiration metadata includes various aspects. The set of expirationmetadata may be analyzed to identify an expiration trigger that is basedon a temporal feature (e.g., retention policy date, graduation date). Atblock 221, monitoring for the expiration trigger can occur (e.g.,pinging entity systems for user status/presence). In response tomonitoring for the expiration trigger, at block 224 accomplishment ofthe expiration trigger may be determined (e.g., lack of activity of anelectronic account for a threshold period of time). In response todetermining accomplishment of the expiration trigger the expirationevent can be instantiated (e.g., begin addressing the matter theexpiration metadata was intended to indicate) at block 227. Theexpiration event indicates when a particular block is ready to beexpired without respect to how data is structured or possiblehierarchies. For example, data structure information may have limitedrelevance to removing the particular block.

In response to detecting the expiration event, an expiration operationon the set of blocks is processed at block 250. The expiration stack isused to process the expiration operation. For example, processing in aparticular order as defined by the expiration stack (see block 256).Processing the expiration operation on the set of blocks may includeremoving the set of blocks from the storage system as at block 256. Forexample, once an individual block has expired, the individual block canbe removed from the storage system. Removing can be deleting or, inembodiments, archiving. Such removal may occur regardless of a state ofa backup for an individual file having the individual block. As such, notrace of the individual block may remain.

The storage system may include a set of cloud nodes configured to storethe set of blocks based on the set of expiration metadata. Inembodiments, the set of expiration metadata includes both firstexpiration metadata for a first block of a first file and secondexpiration metadata for a second block of a second file, the set ofblocks includes both the first block and the second block, and the firstfile is different from the second file. As such, by comparing the firstexpiration metadata and the second expiration metadata, a commonexpiration trigger for the first and second blocks may be determined.For example, the common expiration trigger may include a same date(e.g., December 31) for the first and second blocks to be removed. Inother embodiments, the common expiration trigger may be an event count(e.g., when the stock market closes up for 50 days of a given year).

In embodiments, blocks may be physically segregated on storage media sothat location implies a management policy. For example, blocks for usere-mail may be located together in a first region and blocks fororganization tax documents may be located together in a second region.When the first and second blocks share a common expiration trigger, aconcurrent expiration operation for the first and second blocks may beinitiated as at block 253. For example, organization tax documents for agiven year physically located in a given region may employ theconcurrent expiration operation for first and second blocks havingorganization tax documents for the given year. Similarly, if a usere-mail block shares a common expiration trigger with an organization taxdocument block, then the concurrent expiration operation for the firstand second blocks may be initiated. As such, the common expirationtrigger may indicate initiation of the concurrent expiration operationeven if blocks are physically located in different regions.

Method 200 concludes at block 299. Aspects of method 200 may provideperformance or efficiency benefits when managing a set of blocks. Forexample, aspects of method 200 include data storage archival andexpiration management at the block level by a data storage controller toallow associating blocks of different host files based on commonexpiration. Altogether, a storage system may be managed moreefficiently.

FIG. 3 shows modules of a system for managing a storage facilityaccording to embodiments. In embodiments, method 200 may be implementedusing one or more modules of FIG. 3. As such, all aspects of thediscussion related to FIG. 2 and method 200 may beused/applied/implemented in the system. The modules of FIG. 3 may beimplemented in hardware, software or firmware executable on hardware, ora combination thereof. For example, module functionality that may occurin a host device 396 may actually be implemented in a remote device 390and vice versa. Other functionality may be distributed across the hostdevice 396 and the remote device 390. The remote device 390 may havefiles 340 comprising storage blocks 341 having expiration metadata 342.The host device 396 may include a managing module 300.

The managing module 300 may be configured and arranged to manage astorage facility. Managing module 300 can manage a set of blocks in thestorage facility. The managing module 300 may include an establishingmodule 310 (see discussion related to FIG. 2, block 210), a detectingmodule 320 (see discussion related to FIG. 2, block 230), a processingmodule 330 (see discussion related to FIG. 2, block 250), an expirationstack module 351, and a data storage controller module 353.

Aspects of the managing module 300 include policy definition, expirationmanagement, and archival management. The policy definition may allow auser to specify specific management policies for use with user data. Theuser can specify the type of data that belongs in each policy group. Thedata storage controller module 353 may operation a set of controllers(e.g., a controller). When the data is passed to the set of controllersto be written to storage, the set of blocks of data may contain headerinformation that describes the policy that is assigned toeach/particular block of the set of blocks. As the controller processesthe set of blocks, it can record the policies in an internal data store.For the policy groups, the user may specify a retention policy. Theretention policy is how long to keep the particular block after thefirst creation period of the particular block, last referenced period ofthe particular block, or combination of the two. For example, if a taxrelated document must be stored for three years, the set of blocks ofdata associated with that policy may have an expiration date of threeyears after creation. Another example would be where a user would wantto keep all e-mails a minimum of two years and not referenced within sixmonths. After this period, the policy could be set to archive thesee-mails. As both conditions become met, the archival function can betriggered.

Expiration management and archival management may use expirationmetadata stored within the storage controller which has creation dataand reference data for the set of blocks of data. As a particular blockof the set of blocks of data is written within the storage system, it isassigned to one of the predefined policy groups. This data can then begrouped in a region of similar policy data, or the user can elect tohave the data dispersed within the storage subsystem in a manner thatincludes an indication of the policy group it belongs to within theblock (e.g., in the header).

Expiration metadata stored within the controller can be organized, forexpiration processing, in a (first-in-first-out) expiration stack for agiven policy using the expiration stack module 351. As an expirationtrigger (e.g., date) of a block of the set of blocks meets theexpiration criteria (e.g., occurrence of expiration event), theexpiration metadata for the block of the set of blocks of storage may betogether/adjacent in the expiration stack(s). Those blocks may then beremoved via an expiration operation and the areas can be made availableto be reused by other blocks of data. After processing the expirationoperation, the storage subsystem may no longer contain those blocks ofdata. An attempt to reference those blocks may result in a block notfound condition and no data may be returned on the access request.

A controller may maintain information regarding blocks that it has beengiven control of and their location. If a policy of a particular blockindicates that the data has been off-loaded to a different storagemedium (e.g., tape or slower disks), the controller can track where thedata has been sent for future references for the data. Similarly, if ablock has reached an expiration event and the policy indicates to deletethe data, the controller can track that these blocks have been deleted,and can send an appropriate message back to the file system.

Processing an expiration operation that includes archival may similarlycreate a first-in-first-out stack for a given policy. As an individualblock of data meets the archival criteria selected by the user, theindividual block of data is not deleted but it is instead moved to aslower less expensive storage media, such as tape. The block tapelocation is then added to an archival mapping structure data base. Whena request for this block is received by the storage subsystem, and isnot found to be primary tier location, the archival mapping structure isused to identify the location of the block. The block is then retrievedback to the primary tier media and the access request may be put into await condition until the block is retrieved. Blocks can be grouped insuch a fashion that multiple archived blocks can be retrieved when anyone of the blocks are referenced.

Aspects of managing module 300 may provide performance or efficiencybenefits when managing a set of blocks. For example, aspects of managingmodule 300 include data storage archival and expiration management atthe block level by a data storage controller to allow associating blocksof different host files based on common expiration. Altogether, astorage facility may be managed more efficiently.

In addition to embodiments described above, other embodiments havingfewer operational steps, more operational steps, or differentoperational steps are contemplated. Also, some embodiments may performsome or all of the above operational steps in a different order. Themodules are listed and described illustratively according to anembodiment and are not meant to indicate necessity of a particularmodule or exclusivity of other potential modules (or functions/purposesas applied to a specific module).

In the foregoing, reference is made to various embodiments. It should beunderstood, however, that this disclosure is not limited to thespecifically described embodiments. Instead, any combination of thedescribed features and elements, whether related to differentembodiments or not, is contemplated to implement and practice thisdisclosure. Many modifications and variations may be apparent to thoseof ordinary skill in the art without departing from the scope and spiritof the described embodiments. Furthermore, although embodiments of thisdisclosure may achieve advantages over other possible solutions or overthe prior art, whether or not a particular advantage is achieved by agiven embodiment is not limiting of this disclosure. Thus, the describedaspects, features, embodiments, and advantages are merely illustrativeand are not considered elements or limitations of the appended claimsexcept where explicitly recited in a claim(s).

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

Embodiments according to this disclosure may be provided to end-usersthrough a cloud-computing infrastructure. Cloud computing generallyrefers to the provision of scalable computing resources as a serviceover a network. More formally, cloud computing may be defined as acomputing capability that provides an abstraction between the computingresource and its underlying technical architecture (e.g., servers,storage, networks), enabling convenient, on-demand network access to ashared pool of configurable computing resources that can be rapidlyprovisioned and released with minimal management effort or serviceprovider interaction. Thus, cloud computing allows a user to accessvirtual computing resources (e.g., storage, data, applications, and evencomplete virtualized computing systems) in “the cloud,” without regardfor the underlying physical systems (or locations of those systems) usedto provide the computing resources.

Typically, cloud-computing resources are provided to a user on apay-per-use basis, where users are charged only for the computingresources actually used (e.g., an amount of storage space used by a useror a number of virtualized systems instantiated by the user). A user canaccess any of the resources that reside in the cloud at any time, andfrom anywhere across the Internet. In context of the present disclosure,a user may access applications or related data available in the cloud.For example, the nodes used to create a stream computing application maybe virtual machines hosted by a cloud service provider. Doing so allowsa user to access this information from any computing system attached toa network connected to the cloud (e.g., the Internet).

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While the foregoing is directed to exemplary embodiments, other andfurther embodiments of the invention may be devised without departingfrom the basic scope thereof, and the scope thereof is determined by theclaims that follow.

What is claimed is:
 1. A system comprising: a memory; and a processorcoupled to the memory, wherein the processor is configured to:establish, in response to a set of write requests to the set of blocks,a set of expiration metadata for the set of blocks, wherein the set ofexpiration metadata includes both first expiration metadata for a firstblock of a first file and second expiration metadata for a second blockof a second file, the set of blocks including both the first block andthe second block and the first file being different from the secondfile, and wherein the first expiration metadata and the secondexpiration metadata include a respective retention policy based on acreation timestamp, a usage timestamp, and reference frequencyinformation; spatially locate the first block and the second block inthe storage system according to the respective retention policy; create,based on the set of expiration metadata, an expiration stack for the setof blocks, the expiration stack organized based on a temporal featurethat includes a common expiration trigger for the set of expirationmetadata, the temporal feature based on a retention termination date anda creation date such that the expiration stack is organized using afirst-in-first-out order based on the retention termination date andthen creation date; compare the first expiration metadata and the secondexpiration metadata to identify the common expiration trigger for thefirst and second blocks; monitor for the common expiration trigger bypinging entity systems for user status; determine accomplishment of theexpiration trigger based on lack of activity of an electronic useraccount for a threshold period of time; and in response to determiningaccomplishment of the expiration trigger, process an expirationoperation on the set of blocks based on the expiration stack; whereinprocessing the expiration operation includes removing the set of blocksfrom the storage system in an order defined by the expiration stack,wherein the set of blocks are removed regardless of a state of a backupfor the first file and the second file.